<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html lang="en">
<head>
<meta name="copyright" content="Copyright (c) IBM Corporation and others 2011, 2014. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<meta http-equiv="Content-Style-Type" content="text/css">
<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
<title>Deprecated API removals</title>
</head>
<body>
<h1>Deprecated API removals</h1>

<p>
  Often there is no sufficiently compelling reason to ever remove deprecated API, so the 
  API may remain in place indefinitely after the release in which it was deprecated. 
  However, there are situations where continuing to maintain the deprecated API 
  creates too high a burden for both API developers and clients: the code bloat of 
  keeping old implementations, the added complexity of multiple redundant APIs, etc.
  For this reason the Eclipse project has a 
  <a href="http://wiki.eclipse.org/Eclipse/API_Central/Deprecation_Policy">policy</a> 
  to occasionally delete deprecated API after providing two years advance notice to clients. 
  This section describes API removals that occurred in this release, and upcoming 
  removals in future releases.
</p>

<p>
Removed APIs in the Luna (4.4) release:
</p>
<ol>
 <li><a href="#workspaceLock">WorkspaceLock</a></li>
 <li><a href="#incrementalProjectBuilder_getRule">IncrementalProjectBuilder#getRule()</a></li>
</ol>

<p>
API removals after June 2014:
</p>
<ol>
 <li><a href="#presentation">Workbench presentation API</a></li>
 <li><a href="#runtime">Eclipse 2.0 runtime model and boot API</a></li>
 <li><a href="#auth">Platform authorization API</a></li>
 <li><a href="#compositeBundles">Composite Bundles</a></li>
 <li><a href="#batchBundleEvent">Batch Bundle Event</a></li>
 <li><a href="#cssextensions">Remove deprecated CSS extension points</a></li>
</ol>

<p>
API removals after June 2015:
</p>
<ol>
 <li><a href="#listenerlist">org.eclipse.jface.util.ListenerList</a></li>
 <li><a href="#tabletreeviewer">TableTreeViewer</a></li>
  <li><a href="#tasklist">org.eclipse.ui.views.tasklist.TaskList</a></li>
</ol>

<hr>




<!-- ############################################## -->

<h2>API removals in this release</h2>

<h3>1. <a name="workspaceLock">WorkspaceLock</a></h3>
<p>
The <code>WorkspaceLock</code> API allowed a special client (usually platform UI) to
hook into the locking protocols used by the workspace implementation. This hook
was used to mitigate deadlocks due to interaction with synchronous SWT events,
and was never intended to be used by other clients. In the 3.0 release this API
was deprecated in favor of a more general API provided by the <code>org.eclipse.core.jobs</code>
bundle. Invoking this API has had no effect since the 3.0 release. The specific API
being removed includes:
</p>
<ul>
<li>The <code>org.eclipse.core.resources.WorkspaceLock</code> class.</li>
<li>The method <code>org.eclipse.core.resources.IWorkspace#setWorkspaceLock</code></li>
</ul>
<p>
For further details or to provide feedback on this change, see <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=311240">bug 311240</a>.
</p>

<h3>2. <a name="incrementalProjectBuilder_getRule">IncrementalProjectBuilder#getRule()</a></h3>
<p>
The <code>IncrementalProjectBuilder#getRule()</code> method returned a scheduling rule 
that was required for building the project by the builder. This method was intended to be used by the builder framework only.
In the 3.6 release this method was deprecated in favor of a more general method <code>IncrementalProjectBuilder#getRule(int, Map)</code>. 
The specific API being removed includes:
</p>
<ul>
<li>The method <code>org.eclipse.core.resources.IncrementalProjectBuilder#getRule()</code></li>
</ul>
<p>
For further details or to provide feedback on this change, see <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=310072">bug 310072</a>.
</p>

<!-- ############################################## -->

<h2>API removals after June 2014</h2>

<h3>1. <a name="presentation">Workbench presentation API</a></h3>
<p>
The workbench <i>presentation API</i> allowed plug-ins to override certain aspects of 
the workbench appearance, such as the shape of view and editor tabs. This mechanism 
is fundamentally incompatible with the pluggable rendering and declarative styling systems 
in Eclipse 4.2, which offer applications complete control over all aspects of the workbench 
layout and style. The following API will be removed:
</p>
<ul>
<li>API package <tt>org.eclipse.ui.presentations</tt></li>
<li>Extension point <tt>org.eclipse.ui.presentationFactories</tt></li>
</ul>
<p>
For further details or to provide feedback on this change, see <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=370248">bug 370248</a>.
</p>

<h3>2. <a name="runtime">Eclipse 2.0 runtime model and boot API</a></h3>
<p>
When the Eclipse runtime transitioned to use OSGi as its implementation, some existing
APIs for interacting with the old runtime were deprecated and moved to a compatibility fragment
(<tt>org.eclipse.core.runtime.compatibility</tt>). All API that was still valid was moved
elsewhere. These APIs have been non-functional since Eclipse 3.0 and will therefore
be removed in the future. The following packages will be removed:
</p>
<ul>
 <li><tt>org.eclipse.core.boot</tt></li>
 <li><tt>org.eclipse.core.runtime.model</tt></li>
 </ul>
 The compatibility fragment, <tt>org.eclipse.core.runtime.compatibility</tt> will
 also be removed.
<p>
For further details or to provide feedback on this change, see <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=370248">bug 370248</a>.
</p>

<h3>2. <a name="eclipse2view">Eclipse 2.0 ICompatibleWorkbenchPage</a></h3>
<p>
Eclipse 4.4 removed the support for Eclipse 2.0 plug-ins. We will therefore remove the <code>ICompatibleWorkbenchPage</code> interface and the <code>org.eclipse.ui.workbench.compatibility</code> plug-in after the Luna release.
<p>
For further details or to provide feedback on this change, see <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=431178">bug 431178</a>.
</p>

<h3>3. <a name="auth">Platform authorization API</a></h3>
<p>
Since Eclipse 1.0, the Eclipse Platform class provided API for storing and retrieving
passwords in a keyring file. This API used an inherently insecure method for encrypting 
credentials, and used a custom encryption algorithm that made it difficult for some 
consumers to distribute and export Eclipse-based products. For these and other reasons,
this API was deprecated and replaced in Eclipse 3.4 with a new Equinox secure storage API.
In Eclipse 4.2 the implementation of the old authorization methods was removed, but the API left in place. 
This old API will be removed completely in a future release. The following API methods will
be removed from <tt>org.eclipse.core.runtime.Platform</tt>:
</p>
<ul>
 <li><tt>addAuthorizationInfo(URL serverUrl, String realm, String authScheme, Map info)</tt></li>
 <li><tt>getAuthorizationInfo(URL serverUrl, String realm, String authScheme)</tt></li>
 <li><tt>flushAuthorizationInfo(URL serverUrl, String realm, String authScheme)</tt></li>
 <li><tt>addProtectionSpace(URL resourceUrl, String realm)</tt></li>
 <li><tt>getProtectionSpace(URL resourceUrl)</tt></li>
 </ul>
<p>
For further details or to provide feedback on this change, see <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=370248">bug 370248</a>.
</p>

<!-- ############################################## -->

<h3>4. <a name="compositeBundles">Composite Bundles</a></h3>
<p>
In the Equinox 3.5 release an implementation of an OSGi provisional API was
included for composite bundles.  This API includes all classes from the
<code>org.osgi.service.framework package</code>.  This provisional OSGi API has never been
considered API by Equinox and as such has always been marked as x-internal.
</p>
<p>
The OSGi Alliance has decided to reject this provisional API.  It will never
become a part of the official OSGi specification.  Any users of the
<code>org.osgi.service.framework</code> composite bundle API must migrate to using framework
hooks to provide additional isolation within a single OSGi framework.  See the
sub-packages of <code>org.osgi.framework.hooks</code> for ways to control
visibility and isolation for resolution, bundles and services.  Equinox plans to
remove the <code>org.osgi.service.framework</code> API and composite bundle implementation
in the Summer of 2012 (after the 3.8 release).
</p>
<p>
Equinox also has a region digraph implementation that allows for the definition
and configuration of regions that can be used to isolate bundles.  The region
digraph is built on top of the standard OSGi framework hooks.

The specific API to be removed includes:
</p>
<ul>

<li>The complete org.osgi.service.framework package</li>

</ul>
<p>
For further details or to provide feedback on this change, see <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=345790">bug 345790</a>.
</p>

<!-- ############################################## -->

<h3>5. <a name="batchBundleEvent">Batch Bundle Event</a></h3>
<p>
Since Eclipse 3.1, the Equinox Framework has provided API to allow bundle
listeners to batch bundle events.  This functionality never has been
standardized with OSGi and the approach as several drawbacks that make the
API difficult to use.  For these and other reasons the API package
<tt>org.eclipse.osgi.event</tt> will be removed.
</p>
<p>
For further details or to provide feedback on this change, see <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=407302">bug 407302</a>.
</p>

<h3>6. <a name="cssextensions">Remove deprecated CSS extension points</a></h3>
<p>
Since Eclipse 4.0, the Eclipse platform allows styling based on external CSS files.  During the implementation two experimental
extension points have been created which have been replaced in the meantime.

For this reason the extension points
<tt>org.eclipse.e4.u.css.core.elementProvider</tt> and <tt>org.eclipse.e4.ui.css.swt.property.handler </tt> will be removed.
</p>
<p>
For further details or to provide feedback on this change, see <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=430638">bug 430638</a>.
</p>

<!-- ############################################## -->

<h2>API removals after June 2015</h2>
<h3>1. <a name="listenerlist">org.eclipse.jface.util.ListenerList</a></h3>
<p>
The <code>org.eclipse.jface.util.ListenerList</code> class is deprecated since 2005 and has been replaced by <code>org.eclipse.core.runtime.ListenerList with org.eclipse.core.runtime.ListenerList.IDENTITY</code> as argument.
The <code>org.eclipse.jface.util.ListenerList</code> class is planned to get deleted.
</p>
<p>
For further details or to provide feedback on this change, see <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=431981">bug 431981</a>.
</p>

<h3>2. <a name="tabletreeviewer">TableTreeViewer</a></h3>
<p>
The <code>org.eclipse.jface.viewers.TableTreeViewer</code> class is deprecated since Eclipse 3.1 and has been replaced by <code>TreeViewer</code>.
The <code>org.eclipse.jface.viewers.TableTreeViewer</code>, <code>org.eclipse.swt.custom.TableTree</code> and <code>org.eclipse.swt.custome.TableTreeItem</code> classes are planned to get deleted as well as methods using these types.
</p>
<p>
For further details or to provide feedback on this change, see <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=434575">bug 434575</a>.
</p>

<h3>3. <a name="tasklist">org.eclipse.ui.views.tasklist.TaskList</a></h3>
<p>
The <code>org.eclipse.ui.views.tasklist.TaskList</code> class is deprecated since Eclipse 3.4 and has been replaced by <code>MarkerSupportView</code>.
The <code>org.eclipse.ui.views.tasklist.TaskList</code> class and related classes only used by this class are planned to get deleted.
</p>
<p>
For further details or to provide feedback on this change, see <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=434615">bug 434615</a>.
</p>

<!-- ############################################## -->

</body>
</html>
